[DOCS][ResponseOps][Alerting][9.1]: Add breaking change to CCS-based reporting to 9.1 Kibana release notes #245183
+12
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nastasha-solomon
added
release_note:skip
Contributor
🔍 Preview links for changed docs |
2 tasks
Contributor
💚 Build Succeeded
|
nastasha-solomon
requested review from
florent-leborgne and
wajihaparvez
and removed request for
a team
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Contributes to http://github.com/elastic/docs-content-internal/issues/514 by documenting the breaking change to CCS-based reporting in the 9.1 Kibana release notes.
Also took this opportunity to remove the
%char from some breaking change descriptions (it was commenting out lines).Corresponding fixes
Previews